Skip to content

Enforce provider-only JMSX properties under strictCompliance#1853

Open
pradeep85841 wants to merge 3 commits intoapache:mainfrom
pradeep85841:strict-compliance-provider-jmsx
Open

Enforce provider-only JMSX properties under strictCompliance#1853
pradeep85841 wants to merge 3 commits intoapache:mainfrom
pradeep85841:strict-compliance-provider-jmsx

Conversation

@pradeep85841
Copy link
Copy Markdown
Contributor

  • Throws a MessageNotWriteableException if a client attempts to set JMSXDeliveryCount, JMSXRcvTimestamp, JMSXState, JMSXProducerTXID, or JMSXConsumerTXID.
  • Client-set properties (like JMSXGroupID and JMSXGroupSeq) are completely bypassed and function normally.
  • Added StrictComplianceProviderJMSXPropertyTest using an embedded BrokerService to explicitly verify both strict and legacy behaviors.

@pradeep85841
Copy link
Copy Markdown
Contributor Author

Hi @jbonofre, just a quick ping on this! The changes are pushed with JMSException and the corrected imports. Let me know if anything else is needed

@pradeep85841 pradeep85841 requested a review from jbonofre April 1, 2026 16:58
@jbonofre
Copy link
Copy Markdown
Member

jbonofre commented Apr 1, 2026

@pradeep85841 thanks ! Let me do a new pass.

@pradeep85841
Copy link
Copy Markdown
Contributor Author

Updated the "Wait.waitFor" condition in "testNetworkAdvancedStatistics". The test now waits for the broker to finish updating its background metrics (like enqueues and dequeues) before doing the final checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants